If the issue is around construction of a namespace in a string, you might also look at the Dompdf projecthttps://github.com/[dompdf](https://github.com/dompdf).

If the issue is around construction of a namespace in a string, you might also look at the Dompdf project[https://github.com/dompdf](https://github.com/%5Bdompdf%5D(https://github.com/dompdf)).

this is exactly related to dompdf. with this fix everything started working for us and it seems like there are no errors yet

I'm curious why only these lines prove problematic. There is similar logic in elsewhere in FontLib as well as in Dompdf that builds a string containing a class reference. I would expect similar issues there. I suppose it's possible you're not hitting those in this library and that only FontLib is impacted because another dependency in your project is using the "FontLib" namespace.

I'm curious why only these lines prove problematic. There is similar logic in elsewhere in FontLib as well as in Dompdf that builds a string containing a class reference. I would expect similar issues there. I suppose it's possible you're not hitting those in this library and that only FontLib is impacted because another dependency in your project is using the "FontLib" namespace.

Maybe. There are no more moments like this in this library?

Maybe. There are no more moments like this in this library?

In the file you modified there's this block:

if (!self::$raw) {
  $name_canon = preg_replace("/[^a-z0-9]/", "", strtolower($tag));

  $class = "FontLib\\Table\\Type\\$name_canon";

  if (!isset($this->directory[$tag]) || !@class_exists($class)) {
    return;
  }
}
else {
  $class = "FontLib\\Table\\Table";
}

and in Dompdf there's a few, like this one:

$decorator  = "Dompdf\\FrameDecorator\\$decorator";
$reflower   = "Dompdf\\FrameReflower\\$reflower";

I'm fine to accept the change you made and wait to resolve others when they crop up. I'm not familiar with the tool you're using so I don't know what best practice would be to prevent potential rename misses. And I'm not planning to spend a lot of time researching it since it's not a primary usage scenario.